27.1 User Data Approved checks
You can configure MyID to prevent issuance of credentials to people who have not passed their identity checks, or whose identity checks have expired, using the User Data Approved flag.
27.1.1 Configuring the credential profile
The Require user data to be approved option on a credential profile prevents credentials from being issued unless the user has the User Data Approved flag set on their account. You can use this option to prevent a user from being issued credentials when they have not passed the required identity checks.
See section 11.3.1, Credential profile options for details.
27.1.2 Setting the User Data Approved flag
The User Data Approved flag on a user record in MyID is an indicator that the user has passed all identity checks and is permitted to receive a credential. To set this flag:
-
Use the /api/People/{id}/approve feature of the MyID Core API.
See the MyID Core API guide for details.
-
Use the CardIssuanceApproved node through the Lifecycle API.
See the Lifecycle API guide for details.
-
Use the Approve Person option in the MyID Operator Client.
See the Approving user data section in the MyID Operator Client guide for details.
When you set the User Data Approved flag through the Lifecycle API or MyID Core API, you can also provide a VettingDate – see the API documentation for details.
When you set the User Data Approved flag to No using the Unapprove Person option in the MyID Operator Client, the vetting date is cleared.
Note: When you set the vetting date manually or through the Lifecycle API, it uses a time of 00:00:00 UTC. When you set the vetting date automatically by setting the User Data Approved flag in the MyID Operator Client or by using the MyID Core API, it uses a time of 12:00:00 UTC, and this time is then used for all subsequent vetting dates, including manually-set vetting dates, until you clear the vetting date manually.
The vetting date is used for the vetting date validity check; see section 27.2, Vetting date validity checks for details.